SGI Freeware 1999 August

home *** CD-ROM | disk | FTP | other *** search

/ SGI Freeware 1999 August / SGI Freeware 1999 August.iso / dist / fw_tkcvs.idb / usr / freeware / catman / u_man / cat1 / tkcvs.Z / tkcvs

Wrap

Text File | 1999-04-16 | 70.0 KB | 1,519 lines

ttttkkkkCCCCVVVVSSSS((((nnnn)))) TTTTccccllll (((($$$$DDDDaaaatttteeee:::: 1111999999995555////00006666////22221111 00008888::::00009999::::22226666 $$$$)))) ttttkkkkCCCCVVVVSSSS((((nnnn)))) NNNNAAAAMMMMEEEE tkCVS - a Tk/Tcl Graphical Interface to CVS SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS ttttkkkkccccvvvvssss DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN ttttkkkkCCCCVVVVSSSS is a graphical interface to the CVS (Concurrent Versions System) revision control system. ttttkkkkCCCCVVVVSSSS UUUUSSSSEEEERRRRSSSS GGGGUUUUIIIIDDDDEEEE The following sections provide a working overview of tkCVS. WWWWOOOORRRRKKKKIIIINNNNGGGG WWWWIIIITTTTHHHH ttttkkkkCCCCVVVVSSSS To work with files from the repository using ttttkkkkCCCCVVVVSSSS,,,, first you need to select a directory (sometimes called a _s_a_n_d_b_o_x ) to work in. You can create a subdirectory from your home directory (I use _d_e_v_e_l_o_p for all of my development software, you may like to use _s_r_c or _p_r_o_g_s ), or you may work from your home directory. After selecting this directory and navigating into it using the directory display, you can select a _m_o_d_u_l_e to work with. In CVS, groups of files are arranged into modules for easy access. ttttkkkkCCCCVVVVSSSS arranges modules into _d_i_r_e_c_t_o_r_i_e_s and _s_u_b_d_i_r_e_c_t_o_r_i_e_s in a tree structure much in the same way that you would arrange them in your home directory. You can navigate through the ttttkkkkCCCCVVVVSSSS module tree using the _M_o_d_u_l_e _B_r_o_w_s_e_r window. WWWWoooorrrrkkkkiiiinnnngggg wwwwiiiitttthhhh ffffiiiilllleeeessss ffffrrrroooommmm tttthhhheeee rrrreeeeppppoooossssiiiittttoooorrrryyyy Using the Module Browser window, you can select a module to check out. Each module has a _m_o_d_u_l_e _c_o_d_e which is displayed as you browse through the module tree. When you check out a module, a new directory is created in your working directory with the same name as the module code. You can then change into the new directory that ttttkkkkCCCCVVVVSSSS has created, and all of the files in that module will be in the directory. You can use the simple file management and editing features of ttttkkkkCCCCVVVVSSSS to work with files in this directory, or you may use your own text editor, word processor, or whatever to work with the files. Once you have finished your edits (or whenever you have Page 1 (printed 2/3/99) ttttkkkkCCCCVVVVSSSS((((nnnn)))) TTTTccccllll (((($$$$DDDDaaaatttteeee:::: 1111999999995555////00006666////22221111 00008888::::00009999::::22226666 $$$$)))) ttttkkkkCCCCVVVVSSSS((((nnnn)))) reached a stable stage in your development, or possibly even on a daily basis), you can check files back in to ttttkkkkCCCCVVVVSSSS using the _C_h_e_c_k _I_n button. TTTTaaaaggggggggiiiinnnngggg aaaannnndddd BBBBrrrraaaannnncccchhhhiiiinnnngggg You can tag particular versions of a module or file in the repository. Normally you will do this when your programs are ready to be released into a testing or production environment. Tagging is useful for taking snapshots of what the repository contained at a particular date (for example you can tag all of the files associated with a particular software release). You can also create branches based on tags or on particular versions of the files in the repository. This allows you to go back and fix particular bugs or make important patches to an earlier release of software while still being able to work on the latest version. You can use symbolic tag names to refer to versions of files in the repository, instead of just numeric version numbers. For example you can use the tag name _s_o_f_t_w_a_r_e__r_e_l_e_a_s_e__1__5 to indicate release 1.5 of a group of files destined for a customer site. EEEExxxxppppoooorrrrttttiiiinnnngggg Once a software release has been tagged, you can use a special type of check out called an _e_x_p_o_r_t. This allows you to more cleanly check out files from the repository, without all of the administrivia that _C_V_S requires you to have while working on the files. This type of facility is useful for delivery of a software release to a customer. IIIImmmmppppoooorrrrttttiiiinnnngggg ttttkkkkCCCCVVVVSSSS contains a special dialog to allow users to import new files into the repository. New modules can be assigned places within the repository, as well as descriptive names (so that other people know what they are for). WWWWoooorrrrkkkkiiiinnnngggg iiiinnnnssssiiiiddddeeee tttthhhheeee rrrreeeeppppoooossssiiiittttoooorrrryyyy.... tkCVS contains some features that enable it to work inside the repository. The _m_o_d_u_l_e _b_r_o_w_s_e_r window displays the directories and modules within the repository in a tree structured manner. The module browser also contains a _f_i_l_e _b_r_o_w_s_e_r window that enables you to list the files within the module, and view a specific version of a file. Page 2 (printed 2/3/99) ttttkkkkCCCCVVVVSSSS((((nnnn)))) TTTTccccllll (((($$$$DDDDaaaatttteeee:::: 1111999999995555////00006666////22221111 00008888::::00009999::::22226666 $$$$)))) ttttkkkkCCCCVVVVSSSS((((nnnn)))) The _l_o_g _b_r_o_w_s_e_r window contains a graphical display of a revision log for a file, and enables you to see the differences between two versions of a file by pointing and clicking on the versions in the display. OOOOtttthhhheeeerrrr FFFFeeeeaaaattttuuuurrrreeeessss Other features of ttttkkkkCCCCVVVVSSSS allow you to tag files, add new files or delete files from the repository, or view and print reports about the repository contents. You can also search the module database for module codes, module names, and keywords within a module name. CCCCHHHHEEEECCCCKKKKIIIINNNNGGGG OOOOUUUUTTTT MMMMOOOODDDDUUUULLLLEEEESSSS UUUUSSSSIIIINNNNGGGG ttttkkkkCCCCVVVVSSSS To check out a module, first display the mmmmoooodddduuuulllleeee bbbbrrrroooowwwwsssseeeerrrr dialog using the _M_o_d_u_l_e _B_r_o_w_s_e button. Note that you do not have to check out modules using this dialog -- you can use it for just browsing through the modules in the repository. Once you have found the module you are looking for in the module tree, you can check it out by pressing the _C_h_e_c_k _O_u_t button, or export it using the _E_x_p_o_r_t button (see the section on _E_x_p_o_r_t_i_n_g later in this manual). TTTTAAAAGGGGGGGGIIIINNNNGGGG AAAANNNNDDDD BBBBRRRRAAAANNNNCCCCHHHHIIIINNNNGGGG _C_V_S uses a system of _t_a_g_s to indicate places in the development cycle when the repository (or parts of it) are in a stable state. These tags can be applied to modules in the repository or to files within a module. TTTTaaaaggggggggiiiinnnngggg MMMMoooodddduuuulllleeeessss To tag a module, first select the module using the module browser (note that you may tag a module or a directory tree -- to tag an entire directory tree including all of its sub-directories and modules, select the top level directory of the tree). Enter the _t_a_g _n_a_m_e into the _T_a_g _A entry box. Note that a tag name may be any alphanumberic string, but may not contain any spaces. Sample tag names include things like _s_o_f_t_w_a_r_e__r_e_l_e_a_s_e__1__0 or _i_n_t_e_g_r_a_t_i_o_n__t_e_s_t__r_e_l_e_a_s_e. If you also enter a tag name into the Tag B entry box, then all files in that module that are currently tagged with Tag B will be also tagged with Tag A. Select the TTTTaaaagggg---->>>>TTTTaaaagggg MMMMoooodddduuuulllleeee menu item from the menu on the Module Browser dialog, and the module or directory will be tagged with the tag name that you have entered. TTTTaaaaggggggggiiiinnnngggg FFFFiiiilllleeeessss You may tag individual files from within the directory browser. This is mostly useful when you only want to Page 3 (printed 2/3/99) ttttkkkkCCCCVVVVSSSS((((nnnn)))) TTTTccccllll (((($$$$DDDDaaaatttteeee:::: 1111999999995555////00006666////22221111 00008888::::00009999::::22226666 $$$$)))) ttttkkkkCCCCVVVVSSSS((((nnnn)))) tag part of the files in a module, or when you are re- tagging certain files within an already tagged module. Select the files that are to be tagged, and select the FFFFiiiilllleeee---->>>>TTTTaaaagggg FFFFiiiilllleeeessss option from the menu. This will request that you enter a tag name. The selected files will then be tagged with this tag name. UUUUppppddddaaaattttiiiinnnngggg ttttoooo aaaa TTTTaaaagggg Once a file or module has been tagged within the repository, you may use the tag name for checking out files, or updating files to a tag name. If a tag name is entered in the _T_a_g _A field of the browser window when you select a module for check out, then the tagged version of the module (rather than the latest version) will be checked out of the repository. Similarly, instead of selecting File->Update to Head from the main menu, you can select FFFFiiiilllleeee---->>>>UUUUppppddddaaaatttteeee ttttoooo TTTTaaaagggg to update a file to a tagged version (instead of the head version). This will ask you to enter a tag name before the module is updated. BBBBrrrraaaannnncccchhhhiiiinnnngggg CVS also supports the concept of branching files. When you are applying a tag, the tag may be applied as a _b_r_a_n_c_h _t_a_g, which means that all versions based on this tag will be placed on a branch of the main version tree instead of on the trunk. You should update files to a branch tag before you change them if you want your changes to not affect the head version. To read more about branching and branch tags, read the _c_v_s manual page. EEEEXXXXPPPPOOOORRRRTTTTIIIINNNNGGGG An important use of tagging modules is to indicate when a new release of software is ready to be delivered, and to mark the versions of all of the files in that release within the repository. When a release is about to be made, you may _e_x_p_o_r_t it from the repository. This is like a check-out, except for the following: **** Exported directories do not contain the _C_V_S or _C_V_S._a_d_m administrative directories, and are therefore cleaner (but cannot be used for checking files back in to the repository). Page 4 (printed 2/3/99) ttttkkkkCCCCVVVVSSSS((((nnnn)))) TTTTccccllll (((($$$$DDDDaaaatttteeee:::: 1111999999995555////00006666////22221111 00008888::::00009999::::22226666 $$$$)))) ttttkkkkCCCCVVVVSSSS((((nnnn)))) **** Exported files do keyword expansion differently from non-exported files (to ensure that the keyword information is not lost should the file be imported into CVS at a different site). To export a module or directory, press the _E_x_p_o_r_t button at the bottom of the module browser. You must supply a _t_a_g name when you are exporting a module -- you cannot just export the default (head) version. This is to make sure that you have the tag in place so that you can reproduce the exported files at a later date. This is called good _c_o_n_f_i_g_u_r_a_t_i_o_n _m_a_n_a_g_e_m_e_n_t. IIIIMMMMPPPPOOOORRRRTTTTIIIINNNNGGGG NNNNEEEEWWWW MMMMOOOODDDDUUUULLLLEEEESSSS UUUUSSSSIIIINNNNGGGG ttttkkkkCCCCVVVVSSSS Before importing a new module, first check to make sure that you have write permission to the repository. Ask the configuration management staff at your organisation to determine whether you can write to the repository. You should also take some time and view how the repository is structured using the check-out dialog (see above). You will need to provide a directory name for your module (which should not be already in use) and so you will need to know that the parent directory for your module exists in the repository first. Although a module can be imported without the parent directory existing, this means that the CVS _m_o_d_u_l_e_s file must be patched manually after the operation is finised to insert the directory name in the correct place in the file. To import a module, first enter the directory where the module is located. Make sure that there is nothing in this directory except the files that you want to import (create a new empty directory first and copy the files from the module into it if necessary). Once this is done, press the _I_m_p_o_r_t button. You will need to enter the following details: MMMMoooodddduuuulllleeee DDDDiiiirrrreeeeccccttttoooorrrryyyy The location in the module tree where your new module will be put. This directory must not already exist, although its parent directory must exist. MMMMoooodddduuuulllleeee NNNNaaaammmmeeee.... A one-line descriptive name for your module. This is the name that will be displayed in the browser. VVVVeeeerrrrssssiiiioooonnnn NNNNuuuummmmbbbbeeeerrrr The current version number of the module. This should be a number of the form _X._Y._Z where .Y and .Z are optional. You can leave this blank, in which case _1 will be used as the first version number. Page 5 (printed 2/3/99) ttttkkkkCCCCVVVVSSSS((((nnnn)))) TTTTccccllll (((($$$$DDDDaaaatttteeee:::: 1111999999995555////00006666////22221111 00008888::::00009999::::22226666 $$$$)))) ttttkkkkCCCCVVVVSSSS((((nnnn)))) MMMMoooodddduuuulllleeee CCCCooooddddeeee A module code for the module. This code must not already exist in the repository. I strongly suggest that your organisation settles on a single unambiguous code for modules. One possibility is something like: <project code>-<subsystem code>-<module code> Using this scheme, you could have a 3 digit project code, a 3 letter subsystem code, and a 4 letter module code for each module, and everything would be easy to locate. Once you have entered these details, press the _O_K button to import the module. CCCCRRRREEEEAAAATTTTIIIINNNNGGGG NNNNEEEEWWWW DDDDIIIIRRRREEEECCCCTTTTOOOORRRRIIIIEEEESSSS UUUUSSSSIIIINNNNGGGG ttttkkkkCCCCVVVVSSSS ttttkkkkCCCCVVVVSSSS is not a file manager! You can't use it to create directories within your home directory. You can, however, use it to create new directories within the repository. This is best done while importing new modules. If you are about to import a new module, and the parent directory does not exist in the repository, you can create it using the _N_e_w _D_i_r_e_c_t_o_r_y button. Press this button and a dialog will appear allowing you to create the new directory. You must enter the following information: NNNNeeeewwww DDDDiiiirrrreeeeccccttttoooorrrryyyy LLLLooooccccaaaattttiiiioooonnnn Where (within the module tree) the new directory will be created. This directory should not already exist, but the parent directory must exist. NNNNeeeewwww DDDDiiiirrrreeeeccccttttoooorrrryyyy NNNNaaaammmmeeee This is a one-line descriptive name for the new directory. Something like _A_c_c_o_u_n_t_i_n_g _s_o_f_t_w_a_r_e or _T_e_s_t _d_a_t_a _f_o_r _m_y _f_i_l_e_s should be sufficient. Once you have entered this information, press the _O_K button to create the directory. You may use this dialog multiple times in one session to create multiple directories, or an entire tree of directories in your repository. ttttkkkkCCCCVVVVSSSS RRRREEEEFFFFEEEERRRREEEENNNNCCCCEEEE The following sections provide a complete reference to the user interface to tkCVS. Page 6 (printed 2/3/99) ttttkkkkCCCCVVVVSSSS((((nnnn)))) TTTTccccllll (((($$$$DDDDaaaatttteeee:::: 1111999999995555////00006666////22221111 00008888::::00009999::::22226666 $$$$)))) ttttkkkkCCCCVVVVSSSS((((nnnn)))) MMMMAAAAIIIINNNN WWWWIIIINNNNDDDDOOOOWWWW The ttttkkkkCCCCVVVVSSSS main window comprises a menu bar, a current directory display, and some command buttons. MMMMEEEENNNNUUUU The ttttkkkkCCCCVVVVSSSS menu is displayed at the top of the window. There are the following options on the menu: FFFFiiiilllleeee---->>>>OOOOppppeeeennnn This opens the currently marked files so that they can be edited. FFFFiiiilllleeee---->>>>DDDDeeeelllleeeetttteeee This deletes the currently marked files. FFFFiiiilllleeee---->>>>CCCClllleeeeaaaannnnuuuupppp This removes any backup files from the current directory. FFFFiiiilllleeee---->>>>PPPPrrrriiiinnnntttt This prints the currently selected files. For more information on the print command used, see the section on _t_k_C_V_S _c_o_n_f_i_g_u_r_a_t_i_o_n _f_i_l_e_s. FFFFiiiilllleeee---->>>>IIIImmmmppppoooorrrrtttt Select this to import new files into the repository. This is described later. FFFFiiiilllleeee---->>>>CCCCrrrreeeeaaaatttteeee DDDDiiiirrrr Select this to create and name a new directory into the repository. You must create and name a directory before you import files into it. FFFFiiiilllleeee---->>>>TTTTaaaagggg FFFFiiiilllleeeessss Select this to tag some of the files in the current directory. A symbolic tag name must be supplied. If there are files in the current directory display that have been selected, these will be tagged, otherwise all of the files in the current directory will be tagged. FFFFiiiilllleeee---->>>>UUUUppppddddaaaatttteeee Select this to update the files in the current directory to the latest version in the repository. Only files that have changed in the repository since the current directory was checked out will be updated. If there are files in the current display that have been selected, these will be updated, otherwise all of the files in the current directory will be updated. FFFFiiiilllleeee---->>>>UUUUppppddddaaaatttteeee ttttoooo TTTTaaaagggg Select this to update the files in the current directory to a particular tag name. A symbolic tag Page 7 (printed 2/3/99) ttttkkkkCCCCVVVVSSSS((((nnnn)))) TTTTccccllll (((($$$$DDDDaaaatttteeee:::: 1111999999995555////00006666////22221111 00008888::::00009999::::22226666 $$$$)))) ttttkkkkCCCCVVVVSSSS((((nnnn)))) name must be supplied. If there are files in the current display that have been selected, these will be updated, otherwise all of the files in the current directory will be updated. FFFFiiiilllleeee---->>>>AAAAdddddddd FFFFiiiilllleeeessss This is the same as the _A_d_d _F_i_l_e_s button. Press this button to add new files to the repository. The files you have selected will be added to the repository next time you press the _C_h_e_c_k _I_n button. FFFFiiiilllleeee---->>>>RRRReeeemmmmoooovvvveeee FFFFiiiilllleeeessss This is the same as the _D_e_l_e_t_e _F_i_l_e_s button. Press this button to remove the marked files from the repository. FFFFiiiilllleeee---->>>>LLLLoooogggg BBBBrrrroooowwwwsssseeee This option opens the _L_o_g _B_r_o_w_s_e_r window for each of the selected files. FFFFiiiilllleeee---->>>>CCCChhhheeeecccckkkk IIIInnnn This is the same as the _C_h_e_c_k _I_n button. FFFFiiiilllleeee---->>>>CCCChhhheeeecccckkkk OOOOuuuutttt This option opens the _M_o_d_u_l_e _B_r_o_w_s_e_r _w_i_n_d_o_w FFFFiiiilllleeee---->>>>EEEExxxxiiiitttt Select this to quit ttttkkkkCCCCVVVVSSSS.... RRRReeeeppppoooorrrrttttssss---->>>>CCCCVVVVSSSS cccchhhheeeecccckkkk Select this option to run a _c_v_s_c_h_e_c_k command in the current directory. This will list all of the files that need checking in to the repository. All files that have been created but not added to the repository are also listed, as well as any files that have been removed from the directory but not removed from the repository. This is the same as pressing the _C_h_e_c_k button at the bottom of the window. RRRReeeeppppoooorrrrttttssss---->>>>CCCCVVVVSSSS ssssttttaaaattttuuuussss This option will display a status of all of the files in the current directory that are part of CVS (to see what files are missing from CVS or from the current directory, press the _S_t_a_t_u_s button at the bottom of the screen). Each file, along with its version number and the version number contained in the repository, is shown. Page 8 (printed 2/3/99) ttttkkkkCCCCVVVVSSSS((((nnnn)))) TTTTccccllll (((($$$$DDDDaaaatttteeee:::: 1111999999995555////00006666////22221111 00008888::::00009999::::22226666 $$$$)))) ttttkkkkCCCCVVVVSSSS((((nnnn)))) The report may be limited to specific files by selecting them in the file list before choosing this menu option. RRRReeeeppppoooorrrrttttssss---->>>>CCCCVVVVSSSS ddddiiiiffffffff This option will display any differences between the files in the current directory and those in the CVS repository. The report may be limited to specific files by selecting them in the file list before choosing this menu option. RRRReeeeppppoooorrrrttttssss---->>>>CCCCVVVVSSSS lllloooogggg This option will display a version history log of the files in the current directory. The report may be limited to specific files by selecting them in the file list before choosing this menu option. RRRReeeeppppoooorrrrttttssss---->>>>MMMMoooodddduuuulllleeee TTTTrrrreeeeeeee This report shows a formatted (tree structured) view of all of the modules in the repository. It may be seen on the screen, printed to a PostScript printer, or saved to a file in ASCII format. RRRReeeeppppoooorrrrttttssss---->>>>MMMMoooodddduuuulllleeeessss SSSSoooorrrrtttteeeedddd bbbbyyyy NNNNaaaammmmeeee This report shows an unformatted list of all of the modules in the repository, sorted in alphabetical order by module name. RRRReeeeppppoooorrrrttttssss---->>>>VVVVeeeerrrrssssiiiioooonnnn TTTTrrrreeeeeeee This report is the same as the Module Tree, however it also shows the version number of each file in the modules in the repository. For a very large CVS repository, this command can take a long time to execute, and produce a very large output, so be careful! RRRReeeeppppoooorrrrttttssss---->>>>VVVVeeeerrrrssssiiiioooonnnn LLLLiiiissssttttiiiinnnngggg bbbbyyyy NNNNaaaammmmeeee This report is the same as Modules Sorted by Name, however it also shows the version number of each file in the modules in the repository. For a very large CVS repository, this command can take a long time to execute, and produce a very large output, so be careful! SSSSeeeeaaaarrrrcccchhhh---->>>>SSSSeeeeaaaarrrrcccchhhh RRRReeeeppppoooossssiiiittttoooorrrryyyy bbbbyyyy CCCCooooddddeeee This item allows you to search the modules database for Page 9 (printed 2/3/99) ttttkkkkCCCCVVVVSSSS((((nnnn)))) TTTTccccllll (((($$$$DDDDaaaatttteeee:::: 1111999999995555////00006666////22221111 00008888::::00009999::::22226666 $$$$)))) ttttkkkkCCCCVVVVSSSS((((nnnn)))) a module code. A dialog will appear asking you to enter the module code that you are searching for. The module code must exactly match the code of a module in the database. If it does match, a window will appear telling you the location of that module in the database. If no match is detected, then a window will appear telling you that there is no match. You can enter the module code in either upper or lower case -- the search is case insensitive. SSSSeeeeaaaarrrrcccchhhh---->>>>SSSSeeeeaaaarrrrcccchhhh RRRReeeeppppoooossssiiiittttoooorrrryyyy bbbbyyyy NNNNaaaammmmeeee This item allows you to search the modules database for a module name. A dialog will appear asking you to enter the module name that you are searching for. The module code must exactly match the name of a module in the database. If it does match, a window will appear telling you the location of that module in the database. If no match is detected, then a window will appear telling you that there is no match. You can enter the module name in either upper or lower case -- the search is case insensitive. SSSSeeeeaaaarrrrcccchhhh---->>>>SSSSeeeeaaaarrrrcccchhhh RRRReeeeppppoooossssiiiittttoooorrrryyyy bbbbyyyy KKKKeeeeyyyywwwwoooorrrrdddd This item allows you to search the modules database for a particular word. A dialog will appear asking you to enter the word that you are searching for. The word can be a module name, a module code, or part of a module name or code. The entire database will be searched for any module whose name or code either completely or partially matches the word you have entered. If a match is found, then a window will appear telling you the location of any modules that match. There may be lots of matches, in which case you may need to scroll the window to see all of them. The search is case insensitive - you can enter the keyword in either capitals or lower case. OOOOppppttttiiiioooonnnnssss---->>>>SSSShhhhoooowwww hhhhiiiiddddddddeeeennnn ffffiiiilllleeeessss This item turns on and off the display of hidden files in the current directory. Hidden files are those files whose name begins with a "." (dot). OOOOppppttttiiiioooonnnnssss---->>>>CCCChhhheeeecccckkkk rrrreeeeccccuuuurrrrssssiiiivvvveeeellllyyyy This item turns on recursive checking of the current directory when the "Check" button at the bottom of the window is pressed. Normally only the files in the current directory are checked. OOOOppppttttiiiioooonnnnssss---->>>>SSSShhhhoooowwww uuuunnnnttttaaaaggggggggeeeedddd ffffiiiilllleeeessss iiiinnnn ttttaaaagggg rrrreeeeppppoooorrrrttttssss When selecting a Version Tree for tagged files from the module browser, normally only the files that have the selected tag are displayed. With this option selected, Page 10 (printed 2/3/99) ttttkkkkCCCCVVVVSSSS((((nnnn)))) TTTTccccllll (((($$$$DDDDaaaatttteeee:::: 1111999999995555////00006666////22221111 00008888::::00009999::::22226666 $$$$)))) ttttkkkkCCCCVVVVSSSS((((nnnn)))) all files will be displayed. The files that do not have the selected tag will show a version number of "missing". HHHHeeeellllpppp---->>>>AAAAbbbboooouuuutttt ttttkkkkCCCCVVVVSSSS This item displays a small dialog that tells you about your release of ttttkkkkCCCCVVVVSSSS.... HHHHeeeellllpppp---->>>>AAAAbbbboooouuuutttt CCCCVVVVSSSS This item displays a small dialog that tells you about your release of CVS. CCCCUUUURRRRRRRREEEENNNNTTTT DDDDIIIIRRRREEEECCCCTTTTOOOORRRRYYYY DDDDIIIISSSSPPPPLLLLAAAAYYYY The current directory display shows: **** The name of the current directory, **** The location of the current directory in the CVS repository. This will only be shown if the current directory is contained in the CVS repository. If it is not contained in the repository you may import it using the _I_m_p_o_r_t button. **** A list of the files in the current directory. You may select a file by clicking on it once with the left mouse button. You may select a group of files by dragging over them with the mouse. Once you have selected files you may mark them. Most of the operations in tkCVS (eg: check in, diff, update) work on the set of marked files. You can mark all of the selected files by using the "Mark Selected" button at the top of the display. You may also mark an individual file by clicking once in the bar on the left hand side of the display next to the file name. Note that marking a file that is already marked un-marks it. You may move into a directory by double-clicking on it. Double clicking on a file will load the file into a simple text editor so you can edit it. FFFFiiiilllleeee SSSSttttaaaattttuuuussss When you are in a directory that is contained in the CVS repository, a file status will be shown next to each file. The various statuses that can be shown are: ooookkkk The file is up to date with respect to the repository. Page 11 (printed 2/3/99) ttttkkkkCCCCVVVVSSSS((((nnnn)))) TTTTccccllll (((($$$$DDDDaaaatttteeee:::: 1111999999995555////00006666////22221111 00008888::::00009999::::22226666 $$$$)))) ttttkkkkCCCCVVVVSSSS((((nnnn)))) ???????????????? The file is not contained in the repository. You may need to add the file to the repository by pressing the "Add" button. LLLLooooccccaaaallllllllyyyy MMMMooooddddiiiiffffiiiieeeedddd The file has been modified in the current directory since being checked out of the repository. LLLLooooccccaaaallllllllyyyy AAAAddddddddeeeedddd The file has been added to the repository. This file will become permanent in the repository once a commit is made. <<<< ddddiiiirrrr >>>> The file is a directory. BBBBUUUUTTTTTTTTOOOONNNNSSSS There are a number of buttons at the bottom of the window. Depending on the setting of your cvscfg(buttons) variable, the buttons may be displayed as text or as bitmaps. Pressing on one of these causes the following actions: CCCChhhheeeecccckkkk Press this button to run a _c_v_s_c_h_e_c_k command in the current directory. This will list all of the files that need checking in to the repository. All files that have been created but not added to the repository are also listed, as well as any files that have been removed from the directory but not removed from the repository. EEEEddddiiiitttt Press this button to load the marked files in to a text editor. DDDDeeeelllleeeetttteeee Press this button to delete the marked files. The files will not be removed from the repository. To remove the files from the repository as well as delete them, press the "Remove" button instead. UUUUnnnnsssseeeelllleeeecccctttt Press this button to un-select all of the selected files. RRRReeeeffffrrrreeeesssshhhh Press this button to re-read the current directory. You might want to do this immediately after a check-in or update, and also if you add new files to the directory. LLLLoooogggg BBBBrrrroooowwwwsssseeee Page 12 (printed 2/3/99) ttttkkkkCCCCVVVVSSSS((((nnnn)))) TTTTccccllll (((($$$$DDDDaaaatttteeee:::: 1111999999995555////00006666////22221111 00008888::::00009999::::22226666 $$$$)))) ttttkkkkCCCCVVVVSSSS((((nnnn)))) This button will bring up the log browser window for each of the selected files in the window. This window is described later. CCCClllleeeeaaaannnnuuuupppp This button deletes all of the backup files in the current directory. Normally you will not want to check these files in to the repository, so you can remove them with this button. Check the tkCVS configuration file to determine the list of files that tkCVS considers to be backup files. AAAAdddddddd FFFFiiiilllleeeessss Press this button when you want to add new files to the repository. You can do this when you have created a new file in the current directory. You must create the file before adding it to the repository. To add some files, first mark them in the list above the buttons. Then press the _A_d_d _F_i_l_e_s button. The files that you have added to the repository will be committed next time you press the _C_h_e_c_k _I_n button. RRRReeeemmmmoooovvvveeee This button will delete files. To delete a file, first mark the file in the list above the buttons. Then press the _R_e_m_o_v_e button. The file will disappear from the directory and from the file list, and will be removed from the repository next time you press the _C_h_e_c_k _I_n button. DDDDiiiiffffffff This compares the marked files with the equivalent files in the repository. Note that a separate program called "TkDiff" (also supplied with tkCVS) is used to do this. For more information on TkDiff, press the help button on the bottom of the TkDiff main window. CCCChhhheeeecccckkkk IIIInnnn This button commits your changes to the repository. This includes adding new files and removing deleted files. When you press this button, a dialog will appear asking you for the version number of the files you want to commit, and a comment. Page 13 (printed 2/3/99) ttttkkkkCCCCVVVVSSSS((((nnnn)))) TTTTccccllll (((($$$$DDDDaaaatttteeee:::: 1111999999995555////00006666////22221111 00008888::::00009999::::22226666 $$$$)))) ttttkkkkCCCCVVVVSSSS((((nnnn)))) You need only enter a version number if you want to bring the files in the repository up to the next major version number. For example, if a file is version _1._1_0, and you do not enter a version number, it will be checked in as version _1._1_1. If you enter the version number _3, then it will be checked in as version _3._0 instead. UUUUppppddddaaaatttteeee This updates your sandbox directory with any changes committed to the repository by other developers. MMMMoooodddduuuulllleeee BBBBrrrroooowwwwsssseeee Press this button to see the Module browser window. This is described later. IIIImmmmppppoooorrrrtttt Press this button to import new files into the repository. This is described later. QQQQuuuuiiiitttt Press this button to leave ttttkkkkCCCCVVVVSSSS.... TTTTHHHHEEEE MMMMOOOODDDDUUUULLLLEEEE BBBBRRRROOOOWWWWSSSSEEEERRRR Most of the file related actions of ttttkkkkCCCCVVVVSSSS are performed within the main window. The module related actions of ttttkkkkCCCCVVVVSSSS are performed within the module browser. The module browser is displayed using the _M_o_d_u_l_e _B_r_o_w_s_e button from the main window. When the dialog is displayed, it shows 3 lists. The first list is the names of all of the items in the repository. The second list shows whether the item is a directory (which may contain other directories or modules), or whether it is a module (which may be checked out from ttttkkkkCCCCVVVVSSSS ). The third list shows the module code or directory location in the repository, for reference. You can double-click on a directory to open it. This displays the name and code of all of the modules and subdirectories within a directory. Double clicking on a directory a second time closes it. You can close the dialog by pressing the _Q_u_i_t button. MMMMoooodddduuuulllleeee BBBBrrrroooowwwwsssseeeerrrr MMMMeeeennnnuuuu The module browser also contains a menu, with the following options: RRRReeeeppppoooorrrrttttssss This menu contains 4 options. These are MMMMoooodddduuuulllleeee TTTTrrrreeeeeeee , Page 14 (printed 2/3/99) ttttkkkkCCCCVVVVSSSS((((nnnn)))) TTTTccccllll (((($$$$DDDDaaaatttteeee:::: 1111999999995555////00006666////22221111 00008888::::00009999::::22226666 $$$$)))) ttttkkkkCCCCVVVVSSSS((((nnnn)))) MMMMoooodddduuuulllleeeessss SSSSoooorrrrtttteeeedddd bbbbyyyy NNNNaaaammmmeeee , VVVVeeeerrrrssssiiiioooonnnn TTTTrrrreeeeeeee , and VVVVeeeerrrrssssiiiioooonnnn LLLLiiiissssttttiiiinnnngggg bbbbyyyy NNNNaaaammmmeeee These perform the same functions as the equivalent items on the ttttkkkkCCCCVVVVSSSS main menu, except for the following note: Each of these options restricts itself to the currently selected module or directory in the module browser. The version reports do not report the head version, instead they report the version number attached to the tag name given in the _T_a_g _A field of the module browser. SSSSeeeeaaaarrrrcccchhhh This menu contains 3 options. These are SSSSeeeeaaaarrrrcccchhhh RRRReeeeppppoooossssiiiittttoooorrrryyyy bbbbyyyy CCCCooooddddeeee , SSSSeeeeaaaarrrrcccchhhh RRRReeeeppppoooossssiiiittttoooorrrryyyy bbbbyyyy NNNNaaaammmmeeee , and SSSSeeeeaaaarrrrcccchhhh RRRReeeeppppoooossssiiiittttoooorrrryyyy bbbbyyyy KKKKeeeeyyyywwwwoooorrrrdddd These perform the same functions as the equivalent items on the ttttkkkkCCCCVVVVSSSS main menu. PPPPaaaattttcccchhhh---->>>>MMMMaaaakkkkeeee PPPPaaaattttcccchhhh FFFFiiiilllleeee This item creates a Larry Wall format patch(1) file in the current directory of the module selected. Note that a tag name must be entered into the _T_a_g _A field of the module browser. If a second tag name is entered into the _T_a_g _B field, then the patch file will contain differences between the two tagged versions of the module. Otherwise the patch file will contain differences between the head version and the tagged version of the module. PPPPaaaattttcccchhhh---->>>>VVVViiiieeeewwww PPPPaaaattttcccchhhh SSSSuuuummmmmmmmaaaarrrryyyy This item displays a short summary of the differences between two versions of a module. Note that a tag name must be entered into the _T_a_g _A field of the module browser. If a second tag name is entered into the field, then the summary will list the changes between the two tagged versions of the module. Otherwise the summary will list differences between the head version and the tagged version of the module. TTTTaaaagggg See the section titled _T_a_g_g_i_n_g _a_n_d _B_r_a_n_c_h_i_n_g for more information on the options on this menu. MMMMoooodddduuuulllleeee BBBBrrrroooowwwwsssseeeerrrr BBBBuuuuttttttttoooonnnnssss The module browser contains the following buttons: Page 15 (printed 2/3/99) ttttkkkkCCCCVVVVSSSS((((nnnn)))) TTTTccccllll (((($$$$DDDDaaaatttteeee:::: 1111999999995555////00006666////22221111 00008888::::00009999::::22226666 $$$$)))) ttttkkkkCCCCVVVVSSSS((((nnnn)))) CCCChhhheeeecccckkkk OOOOuuuutttt Checks out the current version of a module. If a tag name is entered into the _T_a_g _A field, then the tagged version is checked out rather than the head version. EEEExxxxppppoooorrrrtttt See the section titled _E_x_p_o_r_t_i_n_g for more information on exporting modules from the repository. PPPPaaaattttcccchhhh SSSSuuuummmmmmmmaaaarrrryyyy This button displays a short summary of the differences between two versions of a module. Note that a tag name must be entered into the _T_a_g _A field of the module browser. If a second tag name is entered into the _T_a_g _B field, then the summary will list the changes between the two tagged versions of the module. Otherwise the summary will list differences between the head version and the tagged version of the module. FFFFiiiilllleeee BBBBrrrroooowwwwsssseeee Select a module in the module browser and press this button to display the file browser window. QQQQuuuuiiiitttt This button closes the module browser. TTTTHHHHEEEE FFFFIIIILLLLEEEE BBBBRRRROOOOWWWWSSSSEEEERRRR Pressing the _F_i_l_e _B_r_o_w_s_e button in the module browser window displays the ttttkkkkCCCCVVVVSSSS file browser. This window shows a list of each file contained in the selected module, and contains three buttons. These are: VVVViiiieeeewwww This displays a window showing the contents of the file. The file may be viewed but not edited using this window. (To edit a file in the repository, you must check the file out of the repository). Note that if a tag name or version number is entered into the _V_e_r_s_i_o_n / _T_a_g field at the top of the window, the specified version of the file is displayed, and not the head version. LLLLoooogggg This displays the log browser window for the file. QQQQuuuuiiiitttt This button closes the file browser. TTTTHHHHEEEE LLLLOOOOGGGG BBBBRRRROOOOWWWWSSSSEEEERRRR The ttttkkkkCCCCVVVVSSSS _L_o_g _B_r_o_w_s_e_r window enables you to view a graphical display of the revision log of a file, including all previous versions, and any branched versions. You can get to the log browser window in two ways, either by selecting a file within the main window of ttttkkkkCCCCVVVVSSSS and Page 16 (printed 2/3/99) ttttkkkkCCCCVVVVSSSS((((nnnn)))) TTTTccccllll (((($$$$DDDDaaaatttteeee:::: 1111999999995555////00006666////22221111 00008888::::00009999::::22226666 $$$$)))) ttttkkkkCCCCVVVVSSSS((((nnnn)))) pressing the _L_o_g _B_r_o_w_s_e button, or by selecting a file in the file browser window (available from within the module browser) and pressing the _L_o_g _B_r_o_w_s_e button. The two forms of the log browser are slightly different. From within the main window it is possible to perform merge operations on a file, and the results of the merge are stored in the current directory. From within the module browser (working directly within the repository) merge operations are not possible. LLLLoooogggg BBBBrrrroooowwwwsssseeeerrrr WWWWiiiinnnnddddoooowwww The log browser window has three components. These are the file name and version information section at the top, the log display in the middle, and a row of buttons along the bottom. LLLLoooogggg DDDDiiiissssppppllllaaaayyyy The main log display is fairly self explanatory. It shows a group of boxes connected by small lines indicating the main trunk of the file development (on the left hand side) and any branches that the file has (which spread out to the right of the main trunk). Each box contains the version number and author of the version. VVVVeeeerrrrssssiiiioooonnnn NNNNuuuummmmbbbbeeeerrrrssss Once a file is loaded into the log browser, up to two version numbers may be selected. The primary version is selected by clicking the left mouse button on a version box in the main log display. The secondary version (Version B) is selected by clicking the right mouse button on a version box in the main log display. Operations such as "View" and "Merge Branch to Head" always operate only on the primary version selected. Operations such as "Diff" and "Merge Changes to Head" require two versions to be selected. LLLLoooogggg BBBBrrrroooowwwwsssseeeerrrr BBBBuuuuttttttttoooonnnnssss The log browser contains the following buttons: VVVViiiieeeewwww Pressing this button displays a window containing the primary version of the file selected. DDDDiiiiffffffff Pressing this button runs the "tkdiff" program (by John Klassa) to display the differences between version A and version B. Page 17 (printed 2/3/99) ttttkkkkCCCCVVVVSSSS((((nnnn)))) TTTTccccllll (((($$$$DDDDaaaatttteeee:::: 1111999999995555////00006666////22221111 00008888::::00009999::::22226666 $$$$)))) ttttkkkkCCCCVVVVSSSS((((nnnn)))) MMMMeeeerrrrggggeeee BBBBrrrraaaannnncccchhhh ttttoooo HHHHeeeeaaaadddd To use this button, first select a branch version of the file as the primary version. The changes made along the branch up to that version will then be merged into the head version, and stored in the current directory. The version of the file in the current directory will be over-written. MMMMeeeerrrrggggeeee CCCChhhhaaaannnnggggeeeessss ttttoooo HHHHeeeeaaaadddd To use this button, first select two versions anywhere in the file log (although two adjacent branch versions are more commonly selected). It is expected that in most cases version B will be later than version A. CVS will then calculate the changes made between the two versions selected and merge the differences to the head version. Note that if version A is later (higher on the trunk or further along the branch) than version B, a "reverse diff" will be created. This will have the effect of removing the changes from the head version. For example, if the head version is 1.6, version A is 1.5, and version B is 1.3, this button will remove all of the changes made between versions 1.3 and 1.5 from the head version. It may not make sense to select two branch versions on different branches for this function. VVVViiiieeeewwww TTTTaaaaggggssss This button displays a window showing the tags contained in the file. QQQQuuuuiiiitttt This button closes the Log Browser. CCCCOOOONNNNFFFFIIIIGGGGUUUURRRRAAAATTTTIIIIOOOONNNN FFFFIIIILLLLEEEESSSS There are two configuration files for ttttkkkkCCCCVVVVSSSS.... The first is stored in the directory in which the *.tcl files for ttttkkkkCCCCVVVVSSSS are installed. This is called _t_k_c_v_s__d_e_f._t_c_l. Values in this file can be over-ridden by including a ._t_k_c_v_s file in your home directory. Commands in either of these files should be Tcl scripts. In other words, to set a variable name, you should have the following command in your ._t_k_c_v_s file: set <variable-name> <value> Page 18 (printed 2/3/99) ttttkkkkCCCCVVVVSSSS((((nnnn)))) TTTTccccllll (((($$$$DDDDaaaatttteeee:::: 1111999999995555////00006666////22221111 00008888::::00009999::::22226666 $$$$)))) ttttkkkkCCCCVVVVSSSS((((nnnn)))) for example: set cvscfg(papersize) "A4" The following variables are supported by ttttkkkkCCCCVVVVSSSS:::: ccccvvvvssssccccffffgggg((((ppppaaaappppeeeerrrrssssiiiizzzzeeee)))) The paper size to print on. Set this to "A4" for international standard A4 size paper, or "8x11" for US letter paper. ccccvvvvssssccccffffgggg((((ppppooooiiiinnnnttttssssiiiizzzzeeee)))) The basic point size to use in reports. ccccvvvvssssccccffffgggg((((hhhheeeeaaaaddddiiiinnnnggggssssiiiizzzzeeee)))) The point size to use for heading text in reports. ccccvvvvssssccccffffgggg((((ssssuuuubbbbhhhheeeeaaaaddddiiiinnnnggggssssiiiizzzzeeee)))) The point size to use for sub headings in reports. ccccvvvvssssccccffffgggg((((ggggllllbbbb____bbbbaaaacccckkkkggggrrrroooouuuunnnndddd)))) The background colour to use for all items in ttttkkkkCCCCVVVVSSSS.... ccccvvvvssssccccffffgggg((((ggggllllbbbb____hhhhiiiigggghhhhlllliiiigggghhhhtttt)))) The background colour to use for highlighted items. ccccvvvvssssccccffffgggg((((bbbbtttt____llllooooooookkkkhhhheeeerrrreeee)))) The background colour to use for non-highlighted items of particular interest, in particular buttons, scrollbars, etc. ccccvvvvssssccccffffgggg((((bbbbtttt____pppprrrreeeessssssssmmmmeeee)))) The background colour to use for highlighted buttons, scrollbars, etc. ccccvvvvssssccccffffgggg((((ggggllllbbbb____ffffiiiilllleeee____mmmmaaaarrrrkkkk____ccccoooolllloooorrrr)))) The colour to use to indicate marked files. ccccvvvvssssccccffffgggg((((ggggllllbbbb____ddddiiiirrrr____mmmmaaaarrrrkkkk____ccccoooolllloooorrrr)))) The colour to use to indicate directories (which cannot be marked). ccccvvvvssssccccffffgggg((((llllddddeeeettttaaaaiiiillll)))) The default log file detail to be reported; one of "last" (report only the comment from the last checkin); "summary" (version number and comment string for all check-ins); or "verbose" (all logfile detail possible, including symbolic tags). ccccvvvvssssccccffffgggg((((rrrrddddeeeettttaaaaiiiillll)))) The default detail for status reports; one of "terse" (report "status" only and only on those files which are Page 19 (printed 2/3/99) ttttkkkkCCCCVVVVSSSS((((nnnn)))) TTTTccccllll (((($$$$DDDDaaaatttteeee:::: 1111999999995555////00006666////22221111 00008888::::00009999::::22226666 $$$$)))) ttttkkkkCCCCVVVVSSSS((((nnnn)))) not "up-to-date"); "summary" (report the "status" and include "up-to-date"); or "verbose" (provide the report as it would appear unmodified). ccccvvvvssssccccffffgggg((((yyyy____ssssiiiizzzzeeee)))) The number of files that the main working listbox should accomodate. ccccvvvvssssccccffffgggg((((ffffiiiilllleeee____ffffiiiilllltttteeeerrrr)))) The default pattern to be used by the main listbox filter. Use any valid pattern that can be used for a pattern for 'ls'. An empty string is equilivant to the entire directory (minus hidden files). ccccvvvvssssccccffffgggg((((rrrrmmmm____ccccmmmmdddd)))) aaaannnndddd ccccvvvvssssccccffffgggg((((rrrrmmmm____ffffllllaaaaggggssss)))) This determines which operating system command is to be used to delete files. ccccvvvvssssccccffffgggg((((pppprrrriiiinnnntttt____ccccmmmmdddd)))) This determines which operating system command is to be used to print files. ccccvvvvssssccccffffgggg((((cccclllleeeeaaaannnn____tttthhhheeeesssseeee)))) This determines the pattern to be used for cleaning a directory; i.e., the removal of unwanted files. Typically these files are not under CVS. ccccvvvvssssccccffffgggg((((ccccoooonnnnffffiiiirrrrmmmm____pppprrrroooommmmpppptttt)))) This determines the default value for confirmation prompting before performing an operation over selected files. ccccvvvvssssccccffffgggg((((eeeeddddiiiittttoooorrrr)))) To override the default editor (setup when tkcvs is configured and installed) a user can set the cvscfg(editor) variable to the editor of choice in their .tkcvs file (if they have one). Note that the editor must be an Xwindow application. ccccvvvvssssccccffffgggg((((bbbbuuuuttttttttoooonnnnssssttttyyyylllleeee)))) This determines what sort of buttons you get on the main window. TTTTOOOOOOOOLLLLTTTTIIIIPPPPSSSS____OOOOFFFFFFFF ToolTips are the small pop-up descriptions of the buttons that appear under the buttons when the cursor is placed over them. Setting this variable to 1 will turn ToolTips for the main window buttons off. ccccvvvvssss The location of your CVS executable. This can be a full path name or just the string "cvs" in which case your PATH environment variable will be searched for the Page 20 (printed 2/3/99) ttttkkkkCCCCVVVVSSSS((((nnnn)))) TTTTccccllll (((($$$$DDDDaaaatttteeee:::: 1111999999995555////00006666////22221111 00008888::::00009999::::22226666 $$$$)))) ttttkkkkCCCCVVVVSSSS((((nnnn)))) CVS programs. ccccvvvvssssccccffffgggg((((aaaallllllllffffiiiilllleeeessss)))) Set this to 0 to see normal files only in the directory browser, set it to 1 to see all files including hidden files. This option may be turned on and off within the program by using the OOOOppppttttiiiioooonnnnssss---->>>>SSSShhhhoooowwww HHHHiiiiddddddddeeeennnn FFFFiiiilllleeeessss menu option. EEEENNNNVVVVIIIIRRRROOOONNNNMMMMEEEENNNNTTTT VVVVAAAARRRRIIIIAAAABBBBLLLLEEEESSSS You must have the CCCCVVVVSSSSRRRROOOOOOOOTTTT environment variable pointing to the location of your CCCCVVVVSSSS repository before you run ttttkkkkCCCCVVVVSSSS.... UUUUSSSSEEEERRRR CCCCOOOONNNNFFFFIIIIGGGGUUUURRRRAAAABBBBLLLLEEEE MMMMEEEENNNNUUUU EEEEXXXXTTTTEEEENNNNSSSSIIIIOOOONNNNSSSS It is possible to extend the tkCVS menu by inserting additional commands into the ._t_k_c_v_s or _t_k_c_v_s__d_e_f._t_c_l files. These extensions appear on an extra menu to the right of the ttttkkkkCCCCVVVVSSSS OOOOppppttttiiiioooonnnnssss menu. To create new menu entries on the user-defined menu, set the following variables: ccccvvvvssssmmmmeeeennnnuuuu((((ccccoooommmmmmmmaaaannnndddd)))) Setting a variable with this name to a value like "commandname" causes the CVS command "cvs commandname" to be run when this menu option is selected. For example, the following line: set cvsmenu(update_A) "update -A" Causes a new menu option titled "update_A" to be added to the user defined menu that will run the command "cvs update -A" on the selected files when it is activated. (This example command, for versions of CVS later than 1.3, will force an update to the head version of a file, ignoring any sticky tags or versions attached to the file). uuuusssseeeerrrrmmmmeeeennnnuuuu((((ccccoooommmmmmmmaaaannnndddd)))) Setting a variable with this name to a value like "commandname" causes the command "commandname" to be run when this menu option is selected. For example, the following line: set cvsmenu(view) "cat" Causes a new menu option titled "update_A" to be added to the User defined menu that will run the command "cat" on the selected files when it is activated. Any user-defined commands will be passed a list of file Page 21 (printed 2/3/99) ttttkkkkCCCCVVVVSSSS((((nnnn)))) TTTTccccllll (((($$$$DDDDaaaatttteeee:::: 1111999999995555////00006666////22221111 00008888::::00009999::::22226666 $$$$)))) ttttkkkkCCCCVVVVSSSS((((nnnn)))) names corresponding to the files selected on the directory listing on the main menu as arguments. The output of the user defined commands will be displayed in a window when the command is finished. CCCCVVVVSSSS mmmmoooodddduuuulllleeeessss FFFFIIIILLLLEEEE _C_V_S maintains a file called _m_o_d_u_l_e_s in the $CVSROOT/CVSROOT (or $CVSROOT/CVSROOT.adm for versions prior to 1.3) directory in which it stores the location of all of the modules in the CVS repository. ttttkkkkCCCCVVVVSSSS maintains a set of backwards - compatible extensions to this file to store the names of directories and modules. The extensions are: DDDDiiiirrrreeeeccccttttoooorrrryyyy NNNNaaaammmmeeee #D <TAB> _d_i_r_e_c_t_o_r_y <TAB> _d_i_r_e_c_t_o_r_y _n_a_m_e. eg: #D <TAB> source/account/charge <TAB> Charge accounting software MMMMoooodddduuuulllleeee NNNNaaaammmmeeee #M <TAB> _m_o_d_u_l_e _c_o_d_e <TAB> _m_o_d_u_l_e _n_a_m_e Where _m_o_d_u_l_e _c_o_d_e is the same as the module code that CVS uses to refer to the module in the _m_o_d_u_l_e_s file. The #M line must be after the #D line for the directory in which the module is contained, but must be before the line containing the module code line used by CVS. When you are installing ttttkkkkCCCCVVVVSSSS,,,, you may like to add these additional lines to the modules file (remember to check out the _m_o_d_u_l_e_s module from the repository, and then commit it again when you have finished the edits). Note that all of these extension lines commence with a "#" character, and so CVS interprets them as comments. Only ttttkkkkCCCCVVVVSSSS uses them for naming modules. They can be safely left in the file whether you are using ttttkkkkCCCCVVVVSSSS or not (in fact they are a useful reference when browsing your modules file). BBBBUUUUGGGGSSSS Sure. Mostly because I haven't finished it yet. The text editor doesn't work so well with non-ASCII files. If you find any other bugs, write out what you were doing at Page 22 (printed 2/3/99) ttttkkkkCCCCVVVVSSSS((((nnnn)))) TTTTccccllll (((($$$$DDDDaaaatttteeee:::: 1111999999995555////00006666////22221111 00008888::::00009999::::22226666 $$$$)))) ttttkkkkCCCCVVVVSSSS((((nnnn)))) the time the bug happened on the back of a clean $100 note and post it to me. SSSSEEEEEEEE AAAALLLLSSSSOOOO ccccvvvvssss,,,, rrrrccccssss.... AAAAUUUUTTTTHHHHOOOORRRR Del (del@babel.dialix.oz.au) Page 23 (printed 2/3/99)